feat: implement client-side caching for GitHub API responses (closes #33)#54
Open
Ai-chan-0411 wants to merge 1 commit intoO2sa:mainfrom
Open
feat: implement client-side caching for GitHub API responses (closes #33)#54Ai-chan-0411 wants to merge 1 commit intoO2sa:mainfrom
Ai-chan-0411 wants to merge 1 commit intoO2sa:mainfrom
Conversation
…2sa#33) Add in-memory cache with 1-day TTL to reduce GitHub API calls. Cache keyed by username (case-insensitive) to avoid duplicate requests. Extracted reusable InMemoryCache class in lib/cache.ts with configurable TTL constants.
|
@Ai-chan-0411 is attempting to deploy a commit to the osama's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Thank you for the pull request! ✅ A maintainer will review this soon. Please be patient while we take a look. 🙌 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Implements server-side in-memory caching for GitHub API responses to reduce unnecessary API calls.
Changes
InMemoryCacheclass with configurable TTL constants (1 day, 1 hour, 5 minutes)fetchGitHubUserDatato check cache before making API calls; stores result for 1 dayHow it works
github:user:{username}is checked firstBenefits
Closes #33